Real-time order notification processing

ABSTRACT

Real-time order information is published to a server as an order is being placed for a customer and while the order is being fulfilled. The server dynamically pushes in real time the change in state of the order as the order is being fulfilled to a mobile device being operated by the customer.

BACKGROUND

Transaction and order fulfillment processing have become automated in avariety of manners through utilization and deployment of technology. Infact, transactions with businesses can now occur over a variety ofdifferent communication channel, such as: websites, kiosks, mobilephones, and the like.

As a result, consumers engage in transactions with businesses through avariety of devices and interfaces. Further, backend business systemshave automated fulfillment and tracking technology for purposes ofimproved transaction throughput and business efficiency. For instance,package delivery, luggage handling, and even mail delivery utilizes barcodes that are scanned during each stage of package handling. Some ofthese businesses expose that status of package handling to theconsumers, such that the consumers can log into a web site and receive acurrent status and location of their anticipated packages.

Some businesses have even deployed technology to track different stagesof food preparation, such that consumers can interact with a websiteinterface to determine what stage their food order is in at any givenmoment in time.

Most of this technology is passive in the sense that consumers receivenotifications only when requested by the consumer. Furthermore, in mostsituations, the consumer is unable to change or alter orders even withthe technology to request current status updates for the orders.

Additionally, the present technology provided to consumers isproprietary in nature, which means the interfaces are dependent on thebusiness providing the technology to the consumer. This means that theconsumer has to subscribe and interact with multiple differentinterfaces and not all businesses even offer such technology.

Still further, the existing technology does not permit any easymechanism by which the consumer can quickly identify his/her order,modify the order, and collect items to conclude a transaction; rather,the consumer has to repeatedly log into the interface and/or manuallyprovide identification to business personnel to do these types ofactivities with existing approaches.

SUMMARY

In various embodiments, real-time order notification processing ispresented.

According to an embodiment, a method for real-time order notificationprocessing is provided. Specifically, in an embodiment, a change instate to an order while the order is actively being fulfilled by anenterprise is received. Next, the change is dynamically delivered inreal time to a mobile device being operated by a customer associatedwith the order.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram of a system for real-time order notificationprocessing, according to an example embodiment.

FIG. 1B is a diagram a sample architecture for practicing real-timeorder notification processing according to an example embodiment.

FIG. 2 is a diagram of a method for real-time order notificationprocessing, according to an example embodiment.

FIG. 3 is a diagram of another method for real-time order notification,according to an example embodiment.

FIG. 4 is a diagram of a system for real-time order notificationprocessing, according to an example embodiment.

DETAILED DESCRIPTION

FIG. 1A is a diagram of a system 100 for real-time order notificationprocessing, according to an example embodiment. The system 100 is shownschematically in greatly simplified form, with only those componentsrelevant to understanding of one or more embodiments (representedherein) being illustrated. The various components are illustrated andthe arrangement of the components is presented for purposes ofillustration only. It is to be noted that other arrangements with moreor less components are possible without departing from the locationcontext aware computing techniques presented herein and below.

Moreover, various components are illustrated as one or more softwaremodules, which reside in non-transitory storage and/or hardware memoryas executable instructions that when executed by one or more hardwareprocessors perform the processing discussed herein and below.

The techniques, methods, and systems presented herein and below forreal-time order notification processing can be implemented in all, orsome combination of the components shown in different hardware computingdevices having one or more hardware processors.

The system 100 includes an event server 110 having an event manager 111,a variety of Point-Of-Sale (POS) systems 120 having a variety of orderprocessing devices 121, and at least one user-operated device 130 havingprocessing capabilities for processing or remotely accessing (remotefrom the device 130) one or more order interfaces 131.

The event server 130 is a server or a collection of one or more serversremotely located from one another and cooperating as a cloud server.

The event manager 131 is one or more software modules that execute asexecutable instructions on one or more processors of the server 130.

The event manager 131 provides a variety of interfacesaccessible/exposed to the POS system/devices 120 and the orderprocessing devices 121. Moreover, the event manager 131 provides aninterface accessible/exposed to the user-operated device 130 and theorder interface 131.

Initially, a POS system/device 120 subscribes or registers for sendingand receiving event notification with the event manager 111. The exposedinterface of the event manager 111 is adapted to allow the POSsystem/devices 120 to custom-define business-specific order fulfillmentand transaction-related events with the event manager 111. These definedevents are published by the order processing devices 121 to the eventmanager in real time as items are being handled for order fulfillmentwithin an enterprise associated with the POS system/devices 120.

That is, the POS system/devices 120 and the order processing devices 121send in real time order fulfillment events for ongoing transactions.Each event includes a tag or defined structure published and defined tothe event manager 111 during the initial subscription and set-upprocessing for the POS system/devices 120. Following each tag or definedstructure is a payload that can include a variety of information beingpassed by the order processing devices 121 to the event manager, such asa unique transaction identifier, a unique customer identifier, a uniqueitem identifier (for a specific item of the transaction), and anenterprise-specific description, such as but not limited to: orderreceived, item pulled from warehouse (shelf), item packaged, and thelike.

In an embodiment, the descriptions and item detail (description of theitem) may be pulled from a table by the event manager 111 using the tagor tag numbers (published by the POS system/devices 121) as a tableindex. In this way, the descriptions can be controlled and updated bythe POS system/devices 121 by using the exposed interface of the eventmanager to update the table.

It is noted that a variety of other approaches can be used as well, suchas a relational database, etc., that permits meaningful descriptions tobe resolved in real time for item fulfillment notification processing.That is, the event manager 111 is generic enough that published orderfulfillment data can be done in a manner that supports full control toremain with the POS systems/devices 120, such that the event manager 111can support multiple line-of-businesses and/or enterprises and their ownproprietary order fulfillment and transaction processing systems.

The order processing devices 121 can include a variety of enterprisespecific devices, such as but not limited to: handheld scanners,terminals, mobile phones, card readers, sensors, and others. Thesedevices 121 permit reporting activity in an automated fashion to theirown POS system/devices 120, which are then sent to the event manager 111based on the published structure that the POS system/devices 120published with the event manager 111. Thus, as items for a transactionare being processed internal to an enterprise, the current status orstate of the order is being updated in real time through with the POSsystem/devices 120 and provided to the event manager 111.

The event manager 111 also permits a subscription and relevantinterfaces exposed to individual customers and their devices 130. Thecustomer operating one or more customer devices 130 uses an exposedorder interface 131 to subscribe to events published by enterprises fromthe POS system/devices 120. This can be done by the customer on anenterprise-specific bases, done on a customer-defined grouping ofenterprises, or done for any enterprise that is subscribed to the eventmanager 111.

Once the customer is registered and subscribed to receive real-timeorder notifications, the event manager 111 broadcasts events beingreceived in real time for order fulfillment stares or statuses as theyare received from the POS system/devices 120.

Thus, when a change in order fulfillment for an ongoing transaction withan enterprise changes state, the event manager 111 broadcasts the changein state and the order interface 131 identifies the customer-specificorder fulfillment state change details and displays those details inreal-time on the user device 131.

In an embodiment, the user device 130 is a smart watch (as discussedbelow with the discussion of the FIG. 1B). It is noted, however, that inother embodiments the user device 130 can be one of: an intelligentappliance (with network connectivity and processing capabilities), alaptop, a desktop, a network connected vehicle, goggles, and the like.Also, in an embodiment, the user can receive the real-time orderfulfillment state change data on multiple user devices simultaneously.

The real-time notification for order fulfillment state also includes anovel Quick Response (QR) code generated by either the event manager 111or the POS system/devices 120. In the case where the event manager 111generates the QR code, the QR code is in a format that can be read andprocessed by the POS system/devices 120. The QR code is encoded foridentifying and retrieving an entire transaction of the customer that isrelevant to the real-time order fulfillment change in statenotification. This permits the customer to have the QR code scanned froma display of the user-device 130 by a POS device 120. This permits thecustomer to identify his transaction at an enterprise where the order isto be picked up and/or paid for. The QR code can also be automaticallypresented (through a scan at a POS device 120 for order modification(adding an item, deleting an item, or modifying an item or item quantityfor the transaction).

In an embodiment, when the customer is presented on the display with areal-time order notification for a change in state of the order, thecustomer taps the information presented and the order interface 131responds by providing the QR code.

In an embodiment, the QR code can also permit the customer to replay theorder from creation up until the real-time state change notification.For example, activating the QR code with a user touch may display thefollowing, as one example, on the display of the user device 130:transaction initiated on date X for items Y and Z at store A; on dateX+1 a quantity for Y was increased by the customer, on date X+2 new itemQ was added, on X+3 items X and Y pulled from shelves, etc. It is alsonoted that the time of day may be displayed as well. So, the orderinterface 131 interacts with the event manager 111 and can replay anorder on the display of the user device 130.

In an embodiment, double tapping of the QR code (or some other definedinterface action of the order interface (131) can automatically launch abrowser interface to the enterprise POS system 120 and automaticallyprovide the order identifier to recall the customer's order and permitthe customer to directly interface with the POS system 120 (through thebrowser interface) for purposes of making automated changes to theorder. (This can be done when the POS system/device 120 registers andsubscribes with the event manager 111 by providing a Uniform ResourceLocator (URL) link to the event manager 111; an Applicant ProgrammingInterface (API) or identification of a location within the URL forproviding the order identifier can also be defined for the event manager111 to automatically communicate the order identifier on behalf of thecustomer based on the double tap of the QR code.)

In an embodiment, other features with respect to the QR code for theorder can be provided as well. For example, a tap and hold on the QRcode can initiate a voice call with the enterprise servicing the order(again the voice number or Voice-Over Internet Protocol (VOIP) addresscan be configured upon subscription of the POS system 120 with the eventmanager 110).

In an embodiment, the customer can send a Near-Field Communication (NFC)code or data packet from the user device 130 to the POS system/devices120 to recall and identify the order for pickup or modification. Inanother case, any wireless code or data packet can be sent from theorder interface 131 of the user device 130 to the POS system/device torecall and identify the order for pickup or modification.

The system 100 can produce and process a variety of consumer specificscenarios. As one example, consider a consumer that places an order forgroceries that are to be picked up subsequently at a local grocerystore. Suppose the consumer ordered a specific type of bread, bananas,eggs, and milk. Suppose further that when the store clerk is pulling theitems from the grocery shelf that the specific type of bread is not instock and instead the clerk pulls a different bread and notes that inthe mobile scanner (POS device 120) that the clerk uses to scan theitems from the order as the order is being filled at the grocery store.The grocery store POS system 120 relays the order changes when the clerkis scanning to the event manager 111. The event manager 111 pushes thechanges to the consumers watch 130. The consumer sees the change on thewatch 130 taps the information once and receives a QR code for theorder. Next the consumer double taps the QR code and is presented with aweb-based interface for the order with the grocery store and changes theclerk-selected brand of bread to a different brand of bread based on theoriginal brand being out of stock. This is relayed through the POSsystem 120 to the POS device 120 of the clerk while the clerk iscontinuing his journey through the store for the milk relevant to theorder. The clerk then backtracks and gets the new brand desired by thecustomer. When the last item in the order is picked, the customer againgets notification on the watch 130. The customer subsequently comes tothe store; taps his order on his watch display screen; the QR code ispresented on the watch display screen; the customer places the displayunder a POS checkout device 120; a clerk is dispatched to retrieve thegroceries for the order; and the customer is provided his groceries bythe clerk.

Again, this is but one scenario as an infinite number of scenarios areachievable with the teachings presented herein for real-time ordernotification processing.

The system 100 provides a variety of novel benefits and improvements inexisting retail technology, such as but not limited to:

-   -   1) permitting a customer to receive active real-time state        changes occurring with a customer order;    -   2) permitting a customer to quickly recall and identify his/or        order to an existing POS system/device through an automatically        generated code;    -   3) permitting a customer to make real-time changes to an order;        and    -   4) permitting a customer to replay a history from beginning to        then-existing state of the customer's order.

FIG. 1B is a diagram a sample architecture 140 for practicing real-timeorder notification processing according to an example embodiment.

The architecture illustrates a variety of devices (120 and 130) that canbe used by an enterprise in taking an order from a customer, fulfillingand tracking the progress of the order, and concluding the order withthe customer. For example, such devices (120 and 130) can include alaptop (or desktop), a mobile phone, a table, and POS terminal.

Events relevant to the order are communicated in real time from theenterprise devices to the event manager 110 as the order is being filledwithin the enterprise (and based on what was published and configured bythe enterprise) and communicated from the event manager 110 in real timeto the customer (again based on what was subscribed to by the customer)on the customer watch 130. The order interface 131 of the watch permitsthe customer to tap the real time notification to generate a QR code,which can be scanned at an enterprise kiosk (type of POS device 120) forpicking the items of the order up and concluding a transaction with theenterprise. Moreover, as noted above, the order interface 131 can permitthe QR code to be double tapped to allow the customer to change theorder in real time directly with the enterprise web-based POS device120.

These and other embodiments are no discussed with reference to the FIGS.2-4.

FIG. 2 is a diagram of a method 200 for real-time order notificationprocessing, according to an example embodiment. The software module(s)that implements the method 300 is referred to as an “real-time ordernotification manager.” The real-time order notification manager isimplemented as executable instructions programmed and residing withinmemory and/or a non-transitory computer-readable (processor-readable)storage medium and executed by one or more hardware processors of ahardware computing device. The processors of the device that executesthe real-time order notification manager are specifically configured andprogrammed to process the real-time order notification manager. Thereal-time order notification manager has access to one or more networksduring its processing. The networks can be wired, wireless, or acombination of wired and wireless.

In an embodiment, the device that executes the real-time ordernotification manager is a server 110.

In an embodiment, the device that executes the location context awaremanager is a cloud processing environment having a variety of hardwaredevices logically organized as a single processing environment.

In an embodiment, real-time order notification manager is the eventmanager 111.

At 210, the real-time order notification manager receives a change in astate to an order while the order is actively being fulfilled by anenterprise. The order may include 1 or two or more items being purchasedby a consumer through the enterprise.

The term “user,” “consumer,” and “customer” may be used interchangeablyand synonymously herein above and below.

The manner in which the initial order is taken can vary. For instance,the initial order may be taken in person with a clerk of the enterprise,may be taken through an online website interface of the enterprise,and/or may be placed at a kiosk associated with the enterprise.

Moreover, the enterprise has previously registered for order eventpublication with the real-time order notification manager in the mannersdiscussed above with the FIGS. 1A and 1B. Additionally, the consumeroperating a mobile device has previously subscribed to receiving evennotifications for the enterprise with which the order was taken with thereal-time order notification manager in the manners discussed above withthe FIGS. 1A and 1B.

At 220, the real-time order notification manager delivers in real timethe change to a mobile device being operated by a customer associatedwith the order. In an embodiment, the mobile device executes the orderinterface 131 and/or the method 300 discussed below with the FIG. 3. Inan embodiment, the mobile device is a watch as shown in the FIG. 1B. Inan embodiment, the mobile device is an intelligent appliance, a tablet,a mobile phone, or a laptop.

In an embodiment of 210 and 220, at 221, the real-time ordernotification manager identifies the order and the change based onpre-registered definitions for information captured and communicated byPOS devices for the order within the enterprise. This can be donethrough tags and/or data structure definitions with enterprisecontrolled tables as discussed above with the FIGS. 1A and 1B.

In an embodiment, at 222, the real-time order notification managergenerates a machine-readable code (MRC) that unique identifies the orderand provides the MRC to the mobile device of the customer.

In an embodiment of 222 and at 223, the real-time order notificationmanager generates the MRC as a QR code.

In an embodiment of 222 and at 224, the real-time order notificationmanager generates the MRC as an NFC code.

In an embodiment of 222 and at 225, the real-time order notificationmanager provides a line to the mobile device to an online interface ofan enterprise associated with processing the order. In an embodiment,the link is an URL.

In an embodiment of 225 and at 226, the real-time order notificationmanager interacts with the online interface to identify the order in thelink so when accessed by the mobile device, the online interface is in aprocessing state that is ready to receive order changes from the mobiledevice being operated by the customer.

In an embodiment of 225 and at 227, the real-time order notificationmanager causes an establishment of an active session between the onlineinterface and the mobile device (such as through order interface 131)with a preconfigured processing state for the online interface ready toreceive order changes from the mobile device being operated by thecustomer.

In an embodiment of 222 and at 228, the real-time order notificationmanager generates a replay history for a history of the order fromcreation of the order (initial placement of the order by the customer)to the change in state that was communicated at 210 to the mobiledevice. The replay history is provided by the real-time ordernotification manager to the mobile device. This was discussed above withreference to the FIGS. 1A and 1B.

According to an embodiment, at 230, the real-time order notificationmanager relays a message from the mobile device to an online interfaceassociated with the order. This embodiment assumes bidirectionalcommunication between the real-time order notification manager and theonline interface of the enterprise and can be achieved through exposedApplicant Programming Interface (API) calls between the real-time ordernotification manager and the online interface and between the orderinterface 131 of the mobile device and the real-time order notificationmanager.

FIG. 3 is a diagram of another method 300 for real-time ordernotification, according to an example embodiment. The software module(s)that implements the method 300 is referred to as an “mobile ordernotification agent.” The mobile order notification agent is implementedas executable instructions programmed and residing within memory and/ora non-transitory computer-readable (processor-readable) storage mediumand executed by one or more hardware processors of a hardware device.The processors of the device that executes the mobile order notificationagent are specifically configured and programmed to process the mobileorder notification agent. The mobile order notification agent has accessto one or more networks during its processing. The networks can bewired, wireless, or a combination of wired and wireless.

In an embodiment, the device that executes the mobile order notificationagent is the user-operated device 130.

In an embodiment, the device that executes the mobile order notificationagent is a watch (such as the watch shown in the FIG. 1B).

In an embodiment, the device that executes the mobile order notificationagent is one of: an intelligent appliance, a vehicle, a tablet, alaptop, and goggles.

In an embodiment, the mobile order notification agent is the orderinterface 131.

In an embodiment, the mobile order notification agent interacts with theevent manager 111, the method 200, or a combination of the event manager111 and the method 200.

At 310, the mobile order notification agent receives a real-timenotification for a change to an order that is actively being fulfilledby an enterprise on behalf of a customer. The change can be any actiontaken with respect to the order by a POS device of the enterprise thatis published to the event manager 111 or the method 200 (as discussedabove).

At 320, the mobile order notification agent displays data relevant tothe notification on a display of the mobile device. In an embodiment,the display is a watch display in wireless communication to a mobilephone that executes the mobile order notification agent.

According to an embodiment, at 330, the mobile order notification agentdisplays a MRC that uniquely identifies the order with an enterpriseassociated with the order in response to a touch detected on thedisplay. In an embodiment, the mobile order notification agent generatesthe MRC. In an embodiment, the event manager 111 or the method 200generates the MRC and provides back to the mobile order notificationagent for displaying.

In an embodiment of 330 and at 331, the mobile order notification agentdisplays the MRC as a QR code or a barcode.

In an embodiment of 331 and at 332, the mobile order notification agentobtains and displays a replay history for a history of the order fromcreation to the change in response to a second touch detected on thedisplay. The replay history may be obtained by the mobile ordernotification agent from the event manager 111 or the method 200.

In an embodiment of 331 and at 333, the mobile order notification agentpresents on the display an active session with an online interface ofthe enterprise with the active session configured to a state ready toreceive changes to the order in response to a second touch detected onthe display. This permits the customer to make real-time order changeswhile the order is in progress or being fulfilled by the enterprise byconnecting the customer through the mobile device with the onlineordering interface of the enterprise.

In an embodiment, at 340, the mobile order notification agent wirelesslycommunicates the MRC to a POS device at the enterprise forauthenticating to the POS device and collection of items relevant to theorder. Here, this can be the QR code being scanned at a POS device(kiosk or clerk-operated terminal) from the display of the mobile deviceor can be an NFC code tapped on the POS device. The permits automatedcustomer identification and order identification for retrieval at theenterprise or an enterprise store location.

It is to be noted that throughout the discussion herein, the mobiledevice being operated by the customer may be multiple devices wirelesslycommunicating with one another, such as what was discussed above wherethe mobile device is a phone but the display through which the customerinteracts and receives real-time order notifications on is a display ofa watch that is in wireless communication with the customer's mobiledevice.

FIG. 4 is a diagram of a system 400 for real-time order notificationprocessing, according to an example embodiment. The system 400 includesa variety of hardware components and software components. The softwarecomponents of the system 400 are programmed and reside within memoryand/or a non-transitory computer-readable medium and execute on one ormore hardware processors of a hardware device. The system 400communicates one or more networks, which can be wired, wireless, or acombination of wired and wireless.

In an embodiment, the system 400 implements all, any, or somecombination of the processing discussed above with the FIGS. 1A-1B and2-3.

The system 400 includes at least one hardware processor 401 and areal-time order notification manager 402.

In an embodiment, the hardware processor 401 is part of the server 110.

In an embodiment, the hardware processor is part of a cloud processingenvironment.

The real-time order notification manager 402 is configured to: executeon the processor 401, receive real-time changes made to an order whilean order is being processed by Point-Of-Sale (POS) devices of anenterprise, and communicate in real-time the changes to a mobile deviceoperated by a consumer associated with the order.

In an embodiment, the mobile device is a watch. In an embodiment, themobile device is a combination mobile phone and a watch. In anembodiment, the mobile device is one of: an intelligent appliance, atablet, and a laptop.

In an embodiment, the real-time order notification manager 402 isfurther configured to: interact with a mobile agent processing on themobile device to: generate a QR code that uniquely identifies the order,generate a replay history for a history of the order from creation to athen-existing state of the order, and link the mobile device to anonline system of an enterprise associated with the order for receivingorder changes communicated from the mobile device

In an embodiment, the real-time order notification manager 402 is theevent manager 111.

In an embodiment, the real-time order notification manager 402 is themethod 200.

In an embodiment, the real-time order notification manager 402 is acombination of: some or all of the event manager 111 and the method 200.

In an embodiment, the mobile agent is the order interface 131.

In an embodiment, the mobile agent is the method 300.

In an embodiment, the mobile agent is a combination of the orderinterface 131 and the method 300.

In an embodiment, the real-time order notification manager 402 isdeployed as a Software as a Service (SaaS) over a network.

It should be appreciated that where software is described in aparticular form (such as a component or module) this is merely to aidunderstanding and is not intended to limit how software that implementsthose functions may be architected or structured. For example, modulesare illustrated as separate modules, but may be implemented ashomogenous code, as individual components, some, but not all of thesemodules may be combined, or the functions may be implemented in softwarestructured in any other convenient manner.

Furthermore, although the software modules are illustrated as executingon one piece of hardware, the software may be distributed over multipleprocessors or in any other convenient manner.

The above description is illustrative, and not restrictive. Many otherembodiments will be apparent to those of skill in the art upon reviewingthe above description. The scope of embodiments should therefore bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

In the foregoing description of the embodiments, various features aregrouped together in a single embodiment for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting that the claimed embodiments have more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Description of the Embodiments, with each claimstanding on its own as a separate exemplary embodiment.

The invention claimed is:
 1. A method, comprising: registering, byexecutable instructions that are executed by a hardware processor from anon-transitory computer-readable storage medium, events through aPoint-Of-Sale (POS) interface that defines each event as a tag that isto be followed by a specific payload relevant to order processing by aspecific business; storing, by the executable instructions, the eventsin a table; receiving, by the executable instructions, a change in stateto an order while the order is actively being fulfilled by an enterprisebased on received events from a POS device and matched to selective onesof the events in the table; and delivering, by the executableinstructions, in real time the change to a mobile device being operatedby a customer associated with the order; receiving, by the executableinstructions, a response from the mobile device indicating that thecustomer tapped the change on the mobile device; encoding, by theexecutable instructions, an order identifier for the order, a customeridentifier for the customer, the change, and the state in a QuickResponse (QR) code based on the receiving of the response; andproviding, by the executable instructions, the QR code to the mobiledevice, wherein when the QR code is scanned or provided from the mobiledevice to the POS device, the POS device reads the QR code, recalls theorder, and causes the mobile device to launch an interface as a browserinterface on the mobile device, populates the interface with orderdetails for the order, and connects the mobile device to the POS deviceallowing customer interaction to make changes to the order through anexisting POS interface associated with the POS device.
 2. The method ofclaim 1, wherein receiving further includes identifying the order andthe change from the received events.
 3. The method of claim 2, whereindelivering further includes communicating real-time data provided by thePOS device with the change based on particular events and those eventsassociated payloads.
 4. The method of claim 1 further comprising,providing a link to the mobile device to an online interface of anenterprise associated with processing the order.
 5. The method of claim4, wherein providing further includes interacting with the onlineinterface to identify the order in the link so when accessed by themobile device the online interface is in a processing state to receiveorder changes from the mobile device.
 6. The method of claim 4 furthercomprising, causing an establishment of an active session between theonline interface and the mobile device with a processing state ready toreceive order changes from the mobile device.
 7. The method of claim 1further comprising, receiving a second response from the mobile deviceindicating the customer tapped the QR code on the mobile device, andproviding to the mobile device a replay history for a history of theorder from creation to the change, wherein the replay history ispresented on the mobile device.
 8. The method of claim 1 furthercomprising, relaying a message from the mobile device to an onlineinterface associated with the order.
 9. A method, comprising: receiving,by executable instructions executed by a hardware processor of a mobiledevice from a non-transitory computer-readable storage medium, areal-time notification for a change in an order that is actively beingfulfilled by an enterprise; displaying, by the executable instructions,data relevant to the change on a display; receiving, by the executableinstructions, a response indicating that the data was tapped by anoperator of the mobile device; requesting, by the executableinstructions, a Quick Response (QR) encoded with a user identifier forthe user, an order identifier for the user, and the change; obtaining,by the executable instructions, the QR code based on the requesting;receiving, by the executable instructions, a touch on the QR codepresented on the display from the user; providing, by the executableinstructions, an interface for making changes to the order based on thereceiving of the touch; identifying, by the executable instructions, adouble-tap selection on the QR code from the user; and automaticallylaunching, by the executable instructions responsive to the double-tapselection, a browser interface that interacts with an existing interfaceof a Point-Of-Sale (POS) system that is processing the order andautomatically populating the browser interface with order details forthe order.
 10. The method of claim 9 further comprising, obtaining anddisplaying a replay history for a history of the order from creation tothe change in response to a different touch detected on the display. 11.The method of claim 9 further comprising, presenting on the display anactive session with the POS system through the browser interface withthe active session configured to a state ready to receive changes to theorder in response to additional touches and inputs made on the display.12. The method of claim 9 further comprising, wirelessly communicatingthe QR code to a POS device at the enterprise for authenticating to thePOS device and a collection of items relevant to the order.
 13. Asystem, comprising: a hardware processor; a non-transitorycomputer-readable storage medium having executable instructionsrepresenting a real-time order notification manager; and the real-timeorder notification manager when executed by the hardware processor fromthe non-transitory computer-readable storage medium causes the hardwareprocessor to: register events through a Point-Of-Sale (POS) interfacethat defines each event as a tag that is to be followed by a specificpayload relevant to order processing by a specific business; store theevents in a table; receive real-time changes made to an order while anorder is being processed by POS devices of an enterprise by matchingreceive events that are received from the POS interface with theselective ones of the events in the table; communicate in real-time thechanges to a mobile device operated by a consumer associated with theorder; receive a touch indication that was made on a display of themobile device to touch the changes by a user that operates the mobiledevice; encode a user identifier for the user, an order identifier forthe order, and the changes in a Quick Response (QR) code based on thetouch indication; receive a tap indication that was made on the displayof the mobile device to the QR code; and instruct the mobile device toautomatically launch a browser interface for interaction with anexisting interface associated with the POS devices and automaticallypopulated with order details for the order, wherein the browserinterface permits the consumer to make changes to the order throughinteractions of the browser interface with the existing interface of thePOS devices.
 14. The system of claim 13, wherein the real-time ordernotification manager when executed by the hardware processor from thenon-transitory computer-readable storage medium causes the hardwareprocessor further causes the hardware processor to: interact with amobile agent processing on the mobile device to: a) generate a replayhistory for a history of the order from creation to a then-existingstate of the order based on a double tap on the QR code made by theuser.
 15. The system of claim 13, wherein the mobile device is aprocessor-enabled watch.